Release 10.1A: OpenEdge Data Management:
Database Administration

PROCOPY utility

Copies an existing database.

Syntax

procopy source-db-name target-db-name [-newinstance ] [-silent]

Parameters

source-db-name

Specifies the database you want to copy. You cannot copy the database if you have a server running on it.

target-db-name

Specifies the structure file or the new database. If you specify a directory without a filename, PROCOPY returns an error.

The value you specify can be any combination of letters and numbers, starting with a letter. Do not use Progress 4GL keywords or special characters, such as commas or semicolons. The maximum length of target-db-name varies depending on the underlying operating system. For specific limits, see your operating system documentation.

-newinstance

Specifies that a new GUID be created for the target database.

-silent

Suppresses the output of work-in-progress messages.

PROCOPY copies a source database to a target database. If the target database exists, it must contain at a minimum the same type and number of storage areas and same extent types as the source database. However, the number of extents in the storage areas of the target database do not need to match the number of extents in the source database. PROCOPY will extend the existing extents in the target database to accommodate the possible increase in size.

If a target database does not exist, PROCOPY creates one using an existing .st file in the target database directory. If a .st file does not exist, PROCOPY creates the target database using the structure of the source database and places all of the extents in the same directory as the target database .db file, even when the source database resides in multiple directories.

Notes

If you do not supply the .db extension for databases, PROCOPY automatically appends it.
A target database must contain the same physical structure as the source. For example, it must have the same number of storage areas, records, blocks, blocksize, and cluster size.
PROCOPY supports the use of internationalization startup parameters such as -cpinternal codepage and -cpstream codepage. See Chapter 18, "Database Startup Parameters," for a description of each database-related internationalization startup parameter.
Databases from releases prior to 10.1A do not have the schema support for a database GUID. When copying one of these older databases, the GUID field will not be added to the database. If the -newinstance qualifier is used, it is silently ignored. Use PROUTIL UPDATESCHEMA to determine if your schema is up to date. For more information, see the "PROUTIL UPDATESCHEMA qualifier" section.
Databases supplied in the DLC directory for this release, contain the field for a database GUID, but the field contains the Unknown value (?) rather than a valid GUID. When PROCOPY is used to copy one of these databases, the GUID field of the target database is automatically set.